feat: add assign-prs-to-author reusable workflow#4
Conversation
Extracts the housekeeping workflow that assigns every open PR with no assignees to its author into a reusable workflow_call, so consumer repos carry only a thin scheduled caller instead of a copy. Bot-authored PRs are skipped by default (skip-bots input). Uses the caller's GITHUB_TOKEN, so the calling job grants pull-requests: write + issues: write.
mattmillerai
force-pushed
the
feat/assign-prs-to-author-reusable
branch
from
f4ac048 to
92dcc1a
Compare
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 32 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
3 participants
What
Adds a third reusable workflow to this repo:
assign-prs-to-author.yml. It assigns every open PR with no assignees to its author, so unassigned PRs get routed back to whoever opened them. Bot-authored PRs (Dependabot, Renovate, app tokens) are skipped by default via theskip-botsinput.Extracted from a copy that currently lives in
Comfy-Org/cloud, following the same thin-caller pattern ascursor-reviewanddetect-unreviewed-merge.Why a reusable workflow
It's generic CI housekeeping with zero repo-specific anything — pure
github-scriptovercontext.repo. Hosting it here means consumer repos carry a small scheduled caller instead of a maintained copy (no drift).Permissions
Uses the caller's
GITHUB_TOKEN(no secrets to pass). The calling job must grantpull-requests: writeandissues: write— assignees are set through the issues API.Caller pattern